Systems and Methods for Health Education, Certification, and Recordation

ABSTRACT

A method for health education, certification, and recordation is disclosed. The method may include obtaining, at a server, a user input from a user interface. The user input may define an interval for a desired CPR certification schedule. The method may include generating, at the server, a CPR certification program. Generating the CPR certification program may include generating at least two task groups. Each task group of the at least two task groups may include a healthcare certification task. The method may include administering, at the server, the CPR certification program. Administering the CPR certification program may include assigning, at the interval defined by the user input, one task group of the at least two task groups to a user enrolled in the CPR certification program, and receiving an indication that the enrolled user has completed the healthcare certification task of the assigned one task group.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/576,116, which was filed on Sep. 19, 2019, entitled “Systems andMethods for Health Education, Certification, and Recordation,” which ispending, and the entirety of which is incorporated by reference.

TECHNICAL FIELD

The present disclosure generally relates to healthcare, and moreparticularly, to systems and methods for health education,certification, and recordation.

BACKGROUND

Certain personnel that work at healthcare facilities are required to becertified in certain healthcare protocols, such as cardiopulmonaryresuscitation (CPR). Conventionally, these people renew theircertification by attending a certification class. These classes may lastseveral hours, and the attendee may attend at regular intervals such asevery two years. For busy healthcare workers, attending such a classtakes time away from caring for patients. Furthermore, some healthcareworker may use the skills taught in these certification classes often.These healthcare workers may not need the same amount of in-classtraining or practice as other healthcare workers that do not use thoseskills as often.

Thus, what is needed is are systems and methods that allow healthcareworkers to adjust training programs and that include more flexibility inmeeting healthcare protocol certifications.

SUMMARY

The present disclosure generally relates to healthcare training systemsand methods. More particularly, the present disclosure relates to anovel application of care-based and competency-based training systemsand methods.

The present disclosure, in one embodiment, contemplates a method forhealth education, certification, and recordation. The method may includea computer-implemented cardiopulmonary resuscitation (CPR) certificationmethod. The method may include obtaining, at a server, a user input froma user interface. The user input may define an interval for a desiredCPR certification schedule. The method may include generating, at theserver, a CPR certification program. Generating the CPR certificationprogram may include generating at least two task groups. Each task groupof the at least two task groups may include a healthcare certificationtask. The method may include administering, at the server, the CPRcertification program. Administering the CPR certification program mayinclude assigning, at the interval defined by the user input, one taskgroup of the at least two task groups to a user enrolled in the CPRcertification program, and receiving an indication that the enrolleduser has completed the healthcare certification task of the assigned onetask group.

Another aspect of the disclosure includes a computer-implemented method.The method may include obtaining, at a computing device, an input thatdefines an interval for assigning task groups to an enrolled user. Themethod may include obtaining, at the computing device, a selection of aplurality of healthcare certification tasks. The method may includegenerating, at the computing device, a plurality of task groups. A taskgroup of the plurality of task groups may include a healthcarecertification task of the plurality of healthcare certification tasks.The method may include generating, at the computing device, acertification program corresponding to a healthcare protocol andassociating the plurality of task groups with the certification program.The method may include administering, at the computing device, thecertification program. Administering the certification program mayinclude, in response to the arrival of a first start date, assigning,via the computing device, the task group to the enrolled user enrolledin the certification program, and receiving, at the computing device, anindication that the enrolled user has completed the healthcarecertification task of the task group.

Another aspect of the disclosure may include a computer-implementedmethod. The method may include obtaining, at a server, an input thatdefines an interval for assigning task groups to an enrolled user. Themethod may include obtaining, at the server, a selection of a pluralityof healthcare certification tasks. The method may include generating, atthe server, a plurality of task groups. A task group of the plurality oftask groups may include a healthcare certification task of the pluralityof healthcare certification tasks. The method may include generating aplurality of trigger events. A trigger event of the plurality of triggerevents may include a condition and data linking a first task group ofthe plurality of task groups to a second task group of the plurality oftask groups. The method may include generating, at the server, acertification program corresponding to a healthcare protocol. Generatingthe certification program may include associating the plurality of taskgroups with the certification program. The method may includeadministering, at the server, the certification program. Administeringthe certification program may include, in response to the arrival of afirst start date, assigning the first task group to the enrolled userenrolled in the certification program, and may include, in response tofulfillment of the condition of the trigger event of the first taskgroup, assigning the second task group to the enrolled user.

The present disclosure includes several benefits that overcome theproblems of the prior art. For example, certification programs generatedor administered by the systems and methods of the present disclosureinclude one or more configurations that tailor the certification programto the preferences of enrolled users. The various configurations of thecertification program that can be tailored include an interval(sometimes called a “frequency”) at which users participate inhealthcare certification tasks, the type(s) of users enrolled in thecertification program (e.g., the certification program can be tailoredto emergency room doctors, hospital secretaries, or other roles), andother configurations. The benefits also include, for example, systemsand methods that (1) record events that occur during an encounter with apatient, (2) provide a customized walkthrough of a healthcare protocolto a user based on the user's experience, knowledge, training, or othercharacteristics, and (3) allow a user's participating in an actual orsimulated medical scenario to work toward or maintain certification in ahealthcare protocol.

It is understood that both the foregoing general description and thefollowing detailed description are exemplary and exemplary only, and arenot restrictive of the disclosure as claimed.

The systems and methods disclosed herein improve the functioning ofcomputers. For example, the systems and methods disclosed provideautomated creation of healthcare certification programs and automatedapplication of events performed by healthcare workers that contribute totheir completion of a certification program. The systems and methodsdisclosed allow computers to generate certification programs andhealthcare protocol walkthroughs that are tailored to the specialties ofa healthcare worker. The systems and methods disclosed allow computersto generate healthcare protocol walkthroughs tailored to the specificpatient being cared for based on that patient's characteristics. Thesystems and methods disclosed herein include computer systems that useprogrammable operational characteristics to customize and tailor thecertification programs and healthcare protocol walkthroughs withouttradeoffs in processor performance or increased time spent configuringcertification programs.

The systems and method overcome the shortcomings of previous attempts byallowing personnel to become and stay certified in healthcare protocolswithout having to sacrifice their time in long certification classesevery few years. The systems and methods also allow healthcare workersto apply their skills to maintaining certification, which reduces theamount of time they spend away from patients. The systems and methodstailor certification programs for users based on the users'characteristics and allows the users to performing certifying activitiesat customized intervals.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of the specification, illustrate exemplary embodiments of thedisclosure. Together with the description, they serve to explain theobjects, advantages, and principles of the disclosure. In the drawings:

FIG. 1 is a schematic block diagram illustrating an exemplary system forhealth education, certification, and recordation.

FIG. 2A is a block diagram illustrating an exemplary certificationprogram for health education, certification, and recordation.

FIG. 2B is a block diagram illustrating a portion of an exemplarycertification program for health education, certification, andrecordation.

FIG. 3 is a block diagram illustrating an exemplary encounter record forhealth education, certification, and recordation.

FIG. 4 is a block diagram illustrating an exemplary healthcare protocolwalkthrough for health education, certification, and recordation.

FIG. 5 is a front view illustrating an exemplary user interface forhealth education, certification, and recordation displayed on a clientdevice.

FIG. 6 is a block diagram illustrating an exemplary system for healtheducation, certification, and recordation.

FIG. 7 is a flowchart diagram illustrating an exemplary embodiment of amethod for health education, certification, and recordation.

FIG. 8 is a flowchart diagram illustrating another exemplary embodimentof a method for health education, certification, and recordation.

FIG. 9 is a flowchart diagram illustrating another exemplary embodimentof a method for health education, certification, and recordation.

FIG. 10 is a flowchart diagram illustrating another exemplary embodimentof a method for health education, certification, and recordation.

FIG. 11 is a flowchart diagram illustrating another exemplary embodimentof a method for health education, certification, and recordation.

DETAILED DESCRIPTION Overview

Reference will now be made in detail to exemplary embodiments of thedisclosure, some aspects of which are illustrated in the accompanyingdrawings.

The present disclosure is directed to systems and methods for healtheducation, certification, and recordation. As discussed below, thesystems and methods of the present disclosure may provide a system thecapability to administer a certification program for a healthcareprotocol (e.g., cardiopulmonary resuscitation (CPR) or basic lifesupport (BLS)), healthcare procedure, or healthcare technique(hereinafter, each is referred to as a “healthcare protocol”). Thecertification program includes one or more configurations that maytailor the certification program to the preferences of enrolled users.The various configurations of the certification program that can betailored include an interval at which users participate in healthcarecertification tasks, the type(s) of users enrolled in the certificationprogram, or other configurations. In some embodiments, a user of thesystems and methods disclosed herein may include a healthcare worker, anon-healthcare worker, an administrator at a healthcare facility, oranother type of user.

The present disclosure is also directed to systems and methods that, insome embodiments, provide functionality to record events that occurduring an encounter with a patient. The systems and methods may providea user with a healthcare protocol walkthrough to guide the user isperforming the steps of a healthcare protocol. The present disclosure isalso directed to systems and methods disclosed herein that provide auser the capability to work toward or maintain certification in acertain healthcare protocol in response to participating in a trainingscenario or an actual medical episode.

FIG. 1 depicts one embodiment of a system 100. The system 100 mayinclude a server 110. The server 110 may include modules. The modulesmay carry out functionality of the server 110. In one embodiment, theserver 110 may include an account module 112. The account module 112 maystore data associated with one or more users of the server 110 or one ormore users of the modules of the server 110. The server 110 may includea module 114. The certification module 114 may administer one or morehealthcare protocol certification programs. The server 110 may includean encounter module 116. The encounter module 116 generate an encounterrecord that may include data describing one or more events that occurredduring a patient encounter. The server 110 may include a walkthroughmodule 118. The walkthrough module 118 may store one or more healthcareprotocol walkthroughs. The walkthrough module 118 may customize ahealthcare protocol walkthrough based on received data (e.g., apatient's age, sex, etc.) and may present the healthcare protocolwalkthrough to a user. In some embodiments, the encounter module 116 mayfeed encounter data into the certification module 114, and thecertification module 114 may determine whether an event recorded by theencounter data contributes, at least in part, to a user fulfilling ahealthcare certification task of a certification program the user may beenrolled in.

In one embodiment, the system 100 may include a client device 120. Theclient device 120 may communicate with the server 110 via a data network130 of the system 100. The client device 120 may send data to the server110 or receive data from the server 110. The client device 120 maydisplay the received data. The client device 120 may receive user inputand send data to the server based on the user input. The user input mayinclude input to configure the one or more modules 112, 114, 116, 118 ofthe server 110.

The following describes further details of one or more embodiments ofthe present disclosure. In some embodiments, the system 100 may includea server 110. The server 110 may include one or more computing devices.A computing device may include one or more processors, memory, one ormore input/output (I/O) interfaces, or other computer components. Theserver 110 may include data storage. The data storage may include a filesystem, database, or other data-storing capabilities. The server 110 mayinclude one or more modules. As used herein, the term “module” may referto a software implementation, hardware implementation, or a combinationof both. A module may include functionality that carries out steps,instructions, operations, or the like. A module may be implemented usingprogram instructions, circuitry, or other implementation methods, as aredescribed herein.

In some embodiments, the system 100 may include a client device 120. Aclient device 120 may include a personal computer, a tablet computer, asmartphone, or other computing device. The client device 120 may includesoftware, such as a software application (app), that may performfunctionality, such as communicating with the server 110. In someembodiments, some of the functionality of the one or more modules of theserver 110 may be performed by the client device 120. The client device120 may send data to the server 110 and may receive data from the server110. The client device 120 may display various representations of databased on the data received from the server 110. The server 110 may be indata communication with the client device 120 over a data network 130such as the Internet.

In some embodiments, the system 100 may include a data network 130. Thedata network 130 may allow the server 110, client device 120, and otherdevices to be in data communication. In one embodiment, the data network130 may include a local area network (LAN), wide area network (WAN), theInternet, or other network. The data network 130 may include wired orwireless communication.

In one embodiment, the account module 112 may store, configure, orprocess data associated with one or more user accounts. A user accountmay store data associated with a user of the system 100. A user mayinclude a person that works at a healthcare facility. A user account maystore user personal information data. Personal information data mayinclude the user's name, age, sex, or other personal data. The useraccount may store contact data. Contact data may include the user'saddress, phone number, email address, or other contract information. Theuser account may store occupational data. Occupational data may includeone or more facilities the user works at, whether the user is anon-healthcare worker (e.g., an administrator, janitor, secretary, etc.)or a healthcare worker (e.g., a doctor, nurse, physician assistant,etc.), or one or more of the user's specialties (e.g., emergencymedicine, neurology, oncology, etc.). The user account may storecredential data. Credential data may include information related to theuser's graduation from an educational institution (e.g., a graduationdate, undergraduate institution, medical school, etc.) or licensinginformation (e.g., jurisdictions where the user is licensed, dates ofobtaining a license, expiration date of a license, etc.). The useraccount may store certification information. Certification informationmay include information related to the user's certifications (e.g., alist of healthcare protocols the user is certified in, dates for whichthe user's certifications expire, etc.) The user account may storeprivilege information (e.g., admitting privileges, surgical privileges,prescribing privileges, etc.). The user account may store otherinformation or data.

In one embodiment, the account module 112 may receive data related tothe user of a user account. The account module 112 may update the user'saccount based on the received data. For example, as described below, inresponse to the account module 112 receiving an indication from thecertification module 114 that the user has completed at least a portionof a certification program, the account module 112 may update thecertification data of the user's account. In some embodiments, theaccount module 112 may output data stored in a user account. Forexample, the account module 112 may send user account data to the clientdevice 120 to be viewed by a user.

In some embodiments, the account module 112 may store data only relatedto a user's certification in one or more healthcare protocols. Otherdata, such as electronic healthcare record (EHR) access rights,demographic data, or other data a healthcare computer system may trackmay be stored separately from the account module 112 or the server 110.

Certification Customization

In one embodiment, the server 110 may include the certification module114. The certification module 114 may store one or more certificationprograms. A certification program may include a program administered tousers in order to certify a user in a healthcare protocol. Thecertification module 114 may administer at least a portion of acertification program.

FIG. 2A depicts a data representation of one embodiment of acertification program 200. In some embodiments, the certificationprogram 200 may include a name 202. The name 202 may briefly identifythe certification program 200. The certification program 200 may includea description 204. The description 204 may briefly describe thecertification program 200. In one embodiment, the certification program200 may include a program type 206. The program type 206 may include acategory to which one or more certification programs 200 may belong. Thecertification program 200 may include a certifying body 208. Thecertification program 200 may include a healthcare protocol 210. Thehealthcare protocol 210 may correspond to an actual healthcare protocolin which a participating user may be certified by participating in thecertification program 200. The certification program 200 may include aninterval 212. The interval 212 may indicate how often healthcarecertification tasks, task groups, or other activities are assigned to aparticipating user. The certification program 200 may include one ormore participating users 214. The one or more participating users 214may include one or more users enrolled in the certification program 200.The certification program 200 may include a task plan 220. The task plan220 may include one or more task groups 222(1)-(6). Each task group ofthe one or more task groups 222(1)-(6) may include healthcarecertification tasks that a participating user may complete in order tobecome certified in the healthcare protocol 210 of the certificationprogram 200. It should be noted that while the task plan 220 of FIG. 2Adepicts six task groups 222(1)-(6), a task plan 220 is may include moreor fewer task groups 222(1)-(n). Furthermore, the task plan 220 mayinclude task groups 222(1)-(n) in a different order, with differentpaths through the task groups 222(1)-(n), or with other configurations.

In some embodiments, the name 202 of the certification program 200 mayinclude a string of text. The name 202 may include a name configured bya user of the certification module 114. The name 202 may uniquelyidentify the certification program 200 among multiple certificationprograms 200 stored or administered by the certification module 114. Anexample of a name 202 may include “CPR—Nurses.” In one embodiment, thedescription 204 may include text. The description 204 may furtherdescribe portions of the certification program 204. In some embodiments,the program type 206 may include a category of plans. A category ofplans may include resuscitation, acute care, or another category. Insome embodiments, a certification program 200 may include multipleprogram types 206. For example, a certification program for thehealthcare protocol 210 of using an automated external defibrillator(AED) may include the program type 206 of resuscitation and acute care.In one embodiment, the certifying body 208 may include an organizationor other entity that has the authority to certify persons in thehealthcare protocol. Examples of a certifying body 208 may include theAmerican Red Cross, the American Heart Association, or anotherorganization.

In one embodiment, the healthcare protocol 210 may includecardiopulmonary resuscitation (CPR), a first aid procedure, AED, basiclife support (BLS), advanced life support (ALS), or another healthcareprotocol. The healthcare protocol 210 may correspond to an actualhealthcare protocol that may include a series of steps a user shouldperform in a specified medical situation. For example, one or more stepsa user should perform in response to encountering a person who is notbreathing may include positioning the person on his/her back, checkingfor breathing, administering chest compressions, or blowing into thepersons mouth.

In one embodiment, the interval 212 may include data related to howoften a participating user of the one or more participating users 214 inthe certification program 200 may be assigned a task group of the one ormore task groups 222(1)-(6), healthcare certification task of one ormore healthcare certification tasks 228(1)-(6), or other action relatedto the certification program 200. In one embodiment, the interval 212may include three months, six months, twelve months, 24 months, or someother time interval. The previously mentioned intervals 212 may includeonce every three months, six months, twelve months, or 24 months. Insome embodiments, the interval 212 may include intervals of equal timeor may include intervals of different time lengths. In some embodiments,the interval 212 may be associated with a schedule for the certificationprogram. In other embodiments, a participating user may be able toselect an interval 212 that is convenient to the user's 214 schedule.

In one embodiment, a participating user may include a user with a useraccount administered by the account module 112. In one embodiment, thecertification program 200 may include one or more user groups. Thecertification program 200 including a user group may allow one or moreusers with certain common characteristics to simultaneously participatein the same certification program 200. The certification module 114 maydetermine that users belong in the same user group based on user accountdata. In some embodiments, the certification module 114 may administerdifferent certification programs 200 for the same healthcare protocol210, but to different user groups.

In one embodiment, a user group may be based on one or more usercharacteristics. A characteristic may include a whether a user is ahealthcare worker (e.g., doctor) or non-healthcare worker (e.g.,secretary, lifeguard). A characteristic may include a specialty. Forexample, all neurosurgeons may belong to a first user group, and allintensive care unit (ICU) nurses may belong to a second user group. Acharacteristic may include other user characteristics.

In some embodiments, a certification program 200 may include one or moretask groups 222(1)-(6). In response to a participating user of the onemore participating users 214 completing certain task groups 222(1)-(6)of the certification program 200, the participating user may becomecertified in the associated healthcare protocol 210.

FIG. 2B depicts one embodiment of a portion of the task plan 220 portionof a certification program 200. The following describes the task group222(1), although the description is also applicable to the other taskgroups 222(2)-(6). A task group 222(1) may include a start date 224(1).The start date 224(1) may include a date the task group 222(1) isassigned or available to a user. The task group 222(1) may include a duedate 226(1). The due date 226(1) may include a date by whichparticipating users 214 must complete the task group 222(1). The taskgroup 222(1) may include one or more healthcare certification tasks228(1). The one or more healthcare certification tasks 228(1) mayinclude some action a user in the participating users 214 may perform towork toward completing the task group 222(1). In some embodiments, atask group 222(3) may include a trigger event 230(1). The trigger event230(1) may include a condition under which a task group 222(3) isassigned to a user.

In one embodiment, the certification program 200 may include an order ofthe one or more task groups 222(1)-(6). The order of the one or moretask groups 222(1)-(6) may include a chronological order in which atleast a portion of the task groups 222(1)-(6) may be completed by auser. The order of the one or more task groups 222(1)-(6) may includebranching paths. The certification program 200 may select a branch for auser based on a trigger event 230(1) or 230(2), a user characteristic,or some other data. In some embodiments, in response to a usercompleting the last task group 222(6) of a branch, the certificationprogram 200 may assign the user to another task group 222(1)-(6) (e.g.,the first task group 222(1) of the certification program 200).

As an example, FIG. 2B depicts a portion of one embodiment of the taskplan 220 that includes multiple task groups 222(1)-(6). The task groups222(1)-(6) may include a first task group 222(1). The first task group222(1) may not include any preceding task groups. In response to aparticipating user of the one or more participating users 214 completingthe one or more healthcare certification tasks 228(1) of the task group222(1) and a start date 224(2) of the next task group 222(2) occurring,the participating user may be assigned the subsequent task group 222(2).After completion of the healthcare certification tasks 228(2) of thetask group 222(2), the participating user 214 may be assigned either toa first branch with task group 222(3) or a second branch with task group222(5). To which branch the participating user may be assigned may bebased on the participating user's performance on a healthcarecertification task 228(2), a characteristic of the participating user,or another factor.

In some embodiments, the start date 224(1) may include a date on whichthe task group 222(1) is assigned or available to a participating userof the one or more participating users 214. The task group 222(1) beingassigned to the user may include the user being able to work on the oneor more healthcare certification tasks 228(1) of the task group 222(1).The task group 222(1) being assigned to the user may include the userbeing able to view the task group 222(1) via the user's client device120. In one embodiment, the start date 224(1) may include aday-month-year format, hour-minute-second format, or a combination ofboth.

In some embodiments, the due date 226(1) may include a date on which thetask group 222(1) is due. The task group 222(1) being due may includethat certain healthcare certification tasks 228(1) of the task group222(1) must have been completed by the user on or before the due date226(1). In certain embodiments, the due date 226(1) may be selected asany date that may be convenient for a participating user's schedule. Inone embodiment, the due date 226(1) may include a day-month-year format,hour-minute-second format, or a combination of both.

In some embodiments, the one or more healthcare certification tasks228(1) may include an action the user may complete to work towardcertification in the certification program 200. Healthcare certificationtasks 228(1) may include an educational task. An educational task mayinclude attending an in-class lecture, viewing a slideshow presentation,viewing a video, listening to audio, reading a text, or receivinginformation in another way. In some embodiments, at least a portion ofthe educational task may be provided to the user via the client device120. In one embodiment, a healthcare certification task 228(1) mayinclude a practice task. A practice task may include the user practicingone or more healthcare techniques. A practice task may include a userpracticing on a training mannequin (including a data-enabled trainingmannequin that may receive data from and send data to the server 110),taking a quiz, or performing some other action that helps the userpractice what he or she may have learned from an educational task. Ahealthcare certification task 228(1) may include a demonstration task. Ademonstration task may include the user demonstrating competency in thematerial presented during an educational task. A demonstration task mayinclude the user demonstrating on a training mannequin, the userdemonstrating to a training instructor, a multiple choice or freeresponse test, or other demonstration techniques.

In one embodiment, the certification module 114 may receive data relatedto one or more healthcare certification task 228(1). The certificationmodule 114 may determine from the received data whether the usercompleted the healthcare certification tasks 228(1). For example, thecertification module 114 may receive data indicating whether a userviewed a video, whether a user properly performed on a trainingmannequin, or whether a user earned a certain score on a test. In oneembodiment, a task group 222(1) may include multiple healthcarecertification tasks 228(1). The task group 222(1) may be configured toallow a user to complete the healthcare certification tasks 228(1) of atask group 222(1) in any order or in a certain order specified by thetask group 222(1). In some embodiments, in order to complete the taskgroup 222(1), the user may complete all of the healthcare certificationtasks 228(1) of the task group 222(1), a minimum number of healthcarecertification tasks 228(1), or some other number or selection ofhealthcare certification tasks 228(1).

In some embodiments, a trigger event 230(1) of the task group 222(3) mayinclude the arrival of a date or time. The trigger event 230(1) mayinclude the completion of healthcare certification tasks 228(2) (e.g.,viewing or reading educational material, earning a minimum score on aquiz, etc.), the completion of another task group 222(2), or anotherevent.

In one embodiment, a start date 224(1) or a due date 226(1) may berelative to another date. For example, the due date 226(1) of a taskgroup 222(1) may be 30 days after the start date 224(1). The start date224(3) may be two weeks after the completion of a previous task group222(2).

In some embodiments, the certification module 114 may administermultiple certification programs 200 for the same healthcare protocol210. However, the multiple certification programs 200 may each includedifferent frequencies 212, user groups, task groups 222(1)-(6), ororders of task groups 222(1)-(6). For example, the certification module114 may administer a first CPR certification program 200 for emergencyroom doctors that may include a twelve-month interval 212 and a secondCPR certification program 200 for nurses that may include a three-monthinterval 212. In some embodiments, a healthcare certification task ofthe one or more healthcare certification tasks 228(1)-(6) may beselected from a library of healthcare certification tasks stored by thecertification module 114. The healthcare certification task library maybe associated with the healthcare protocol 210 or certifying body 208 ofthe certification program 200.

In some embodiments, the selection of one element of the certificationprogram 200 may influence the availability of other elements for thecertification program 200. In response to a certification program 200including a certain program type 206, the certification program 200 maybe able to include only certain certifying bodies 208. In response to acertification program 200 including a certain certifying body 208, thecertification program 200 may be able to include only certain healthcareprotocols 210. For example, the American Red Cross may only certifyCPR-related healthcare protocols. In response to selecting “American RedCross” for the certifying body 208, a user may only be able to select“CPR” as a healthcare protocol 210 for the certification program 200. Inone embodiment, the interval 212 may be influenced by the healthcareprotocol 210, certifying body 208, or program type 206. In someembodiments, the healthcare protocol 210 may influence which task groups222(1)-(6) or healthcare certification tasks 228(1)-(6) may be selectedfor a certification program 200. In some embodiments, a healthcareprotocol 210 may be associated with a certifying body 204. For example,the American Red Cross may administer a first CPR certification and theAmerican Heart Association may administer a second CPR certification.

In one embodiment, a user of the certification module 114 may configurea certification program 200. The user may configure one or more aspectsof the certification program 200 such as the name 202, certifying body204, healthcare protocol 206, or the interval 208. The user may selectparticipating users 214. The user may configure other aspects of thecertification program 200.

As an example, a certification administrator of a hospital system mayaccess the certification module 114 through a client device 120. Thecertification administrator may use the certification module 114 togenerate the certification program 200 of the FIG. 2A. In generating thecertification program 200, the certification administrator may choose aname 202, description 204 program type 206, certifying body 208,healthcare protocol 210, and interval 212. The certificationadministrator may generate several task groups 222(1)-(6) in thecertification program's 200 task plan 220. The certificationadministrator may configure trigger events 230(1)-(2), start dates224(1)-(6), and due dates 226(1)-(6) for the task groups 222(1)-(6). Thecertification administrator may select healthcare certification tasks228(1)-(6) from a healthcare certification task library for each taskgroup 222(1)-(6). The certification administrator may add participatingusers 214 or user groups to the certification program 200.

In some embodiments, the certification module 114 may enforce that theone or more task groups 222(1)-(6), healthcare certification tasks228(1)-(6) comply with the requirements of being certified in theselected healthcare protocol 210 for the certification program 200. If acertification administrator user uses the certification module 114 togenerate a certification program 200, and the one or more task groups222(1)-(6) or healthcare certification tasks 228(1)-(6) are insufficientto certify a user in the healthcare protocol 210, then the certificationmodule 114 may notify the certification administrator (e.g., via anerror message, pop-up message, or another type of message on a userinterface) or may not allow the certification administrator to completethe certification program 200. As an example, referring the FIG. 2B, ifthe “CPR Basics” quiz of the healthcare certification task 228(2) isnecessary for a participating user to complete in order to be certifiedin CPR, and the certification administrator does not include thathealthcare certification task in one of the task groups 222(1)-(6), thecertification module 114 may notify the certification administrator ofthe requirement and that the certification program 200, in its currentconfiguration, does not include that requirement.

In some embodiments, the certification module 114 may determine whetherone or more healthcare certification tasks 228(1)-(6) are completed in acorrect order. A healthcare protocol 210 may include an order in which aportion of its tasks must be completed. In response to a certificationadministrator attempting to user the certification module 114 togenerate a certification program 200 with one or more healthcarecertification tasks 228(1)-(6) in an incorrect order, the certificationmodule 114 may notify the certification administrator or may prevent thecertification administrator from completing the configuration of thecertification program 200. For example, as depicted in FIG. 2B, the taskgroup 222(1) includes two healthcare certification tasks 228(1): read“CPR Basics” document and view “CPR Basics” video. The healthcareprotocol 210 may allow a user to complete either task before the other.However, the healthcare protocol 210 may not allow a user to completethe healthcare certification task 228(2), take “CPR Basics” quiz, beforethe user has completed the healthcare certification tasks 228(1). If acertification administrator attempts to include the healthcarecertification task 228(2) before the healthcare certification tasks228(1), the certification module 114 may notify the certificationadministrator of the error.

In one embodiment, the certification module 114 may automaticallygenerate at least a portion of a certification program 200. In someembodiments, the certification module 114 may automatically choose aname 202, description 204, program type 206, certifying body 208,healthcare protocol 210, or interval 212. The certification module 114may automatically generate task groups 222(1)-(6) for the certificationprogram 200. Automatically generating the task groups 222(1)-(6) mayinclude configuring trigger events 230(1)-(2), start dates 224(1)-(6),due dates 226(1)-(6), and may include selecting healthcare certificationtasks 228(1)-(6) for the task groups 222(1)-(6). The certificationmodule 114 may automatically enroll participating users 214 or usergroups. The certification module 114 may automatically enroll theparticipating users 214 or user groups based on characteristics of theparticipating users 214 or user groups.

In one embodiment, the certification module 114 may divide the one ormore healthcare certification tasks 228(1)-(6) for completing thecertification program 200 based on the interval 212. For example, a CPRcertification program 200 may include four hours of educational tasks,three hours of practice tasks, and one hour of demonstration tasks (fora total of eight hours of healthcare certification tasks 228(1)-(6)). Auser may configure the CPR certification program 200 with an interval212 of six-month (i.e., four task groups 222(1)-(4) spread over during atwo-year period). The one or more healthcare certification tasks228(1)-(6) of a certification program 200 may be divided into taskgroups 222(1)-(6) in various ways. In one example, the certificationmodule 114 may split the healthcare certification tasks 228(1)-(6) ofthe CPR certification program 200 into four two-hour certificationoccurrences, each certification occurrence including one or more oftasks. In one example, each two-hour task group 222(1)-(4) may includeone hour of educational tasks, 45 minutes of practice tasks, and fifteenminutes of demonstration tasks. In another example, the first two taskgroups (1)-(2) may include the educational tasks, the third task group222(3) may include the first hour of practice tasks, and the last taskgroup 222(4) may include the last hour of practice tasks and thedemonstration tasks. In some embodiments, the task groups 222(1)-(4) mayeach include tasks that may last different time lengths. For example,the first task group 222(1) may include three hours, the second taskgroup 222(1) may include two hours, the third task group 222(3) mayinclude three hours, and the last task group 222(4) may include onehour. The certification module 114 may divide the one or more healthcarecertification tasks 228(1)-(6) based on other configurations, a sequenceof the one or more healthcare certification tasks 228(1)-(6), or otherfactors.

In one embodiment, the certification module 114 automatically generatinga certification program 200 may include the certification module 114selecting healthcare certification tasks 228(1)-(6) based on aparticipating user's 214 characteristic. The certification module 114may automatically generate a certification program 200 intended to beused by one or more participating users 214 with a certaincharacteristic. The characteristic may include the specialty of theparticipating user 214. For example, the certification module 114 mayautomatically generate a certification program 200 intended foremergency room doctors. Based on that configuration, the certificationmodule 114 may select a set of healthcare certification tasks 228(1)-(6)configured for an emergency room doctor. In another embodiment, inresponse to the certification module 114 automatically generating acertification program 200 intended for participating users 214 that arenon-healthcare workers (e.g., a janitor or lifeguard), the certificationmodule 114 may select a set of healthcare certification tasks 228(1)-(6)that give more detail about the healthcare protocol 210 (because, forexample, a janitor may not be as familiar with the healthcare protocol210 as a healthcare worker).

In some embodiments, the certification module 114 may select one or morehealthcare certification tasks 228(1)-(6) based on a location where thecertification program 200 is intended to be used. For example, inresponse to the certification module 114 generating a certificationprogram 200 intended to be used at a pediatric hospital, thecertification module 114 may select one or more healthcare certificationtasks 228(1)-(6) related to resuscitating children for a CPRcertification program 200. For a certification program 200 intended forparticipating users 214 that work in a nursing home, the certificationmodule 114 may select one or more healthcare certification tasks228(1)-(6) related to resuscitating seniors for a CPR certificationprogram 200. In one embodiment, the certification module 114 may performsome functionality, such as selecting the one or more participatingusers 214 or selecting the one or more healthcare certification tasks228(1)-(6) based on output of an artificial intelligence (Al) engine.

In one embodiment, the certification module 114 may modify acertification program 200. A user may use the certification module 114to modify a certification program 200, or the certification module 114may automatically modify the certification program 200. Modifying thecertification program 200 may include modifying the name 202,description 204, program type 206, etc. Modifying the certificationprogram 200 may include modifying one or more task groups 222(1)-(6).Modifying a task group 222(1) may include adding or removing ahealthcare certification task to/from the one or more healthcarecertification tasks 228(1), adjusting a start date 224(1) or due date226(1), adding or removing a trigger event, adding or removing one ormore participating users 214 or user group, or may include othermodifications.

In some embodiments, the certification module 114 may modify acertification program 200 based on data received by the server 100. Thereceived data may mark a healthcare certification task 228(1)-(6) in ahealthcare certification task library indicating that the healthcarecertification task 228(1)-(6) or a version of the healthcarecertification task 228(1)-(6) should no longer be used. The receiveddata may include a replacement healthcare certification task 228(1)-(6).The certification module 114 may modify a healthcare certification task228(1)-(6) of a certification program 200 to no longer include ahealthcare certification task 228(1)-(6) marked for replacement and toinclude a replacement healthcare certification task 228(1)-(6) orreplacement version. For example, the certification module 114 mayreceive data indicating that an educational video is out-of-date. Thecertification module 114 may receive an up-to-date replacement video.The certification module 114 may remove a healthcare certification task228(1)-(6) that includes the out-of-date video from the certificationprograms 200 and replace the removed healthcare certification tasks228(1)-(6) with a new healthcare certification task 228(1)-(6) theinclude the up-to-date video.

In some embodiments, the library of healthcare certification tasks228(1)-(6) may include healthcare certification tasks 228(1)-(6)provided by a patient safety organization (PSO). The server 110 maydownload the healthcare certification tasks 228(1)-(6) from the PSO,receive push updates, or otherwise receive the healthcare certificationtasks 228(1)-(6) from the PSO. The PSO data may help the certificationmodule 114 to operate data-enabled certification programs 200. In someembodiments, a data-enabled certification program 200 may allowparticipating users 214 to become certified in a healthcare protocol 206based on up-to-date information endorsed by authorized governing bodiesor other healthcare organizations. PSO data may include aggregated,de-identified data. The PSO data may be used for benchmarking.

In one embodiment, the certification module 114 may track aparticipating user's progress in adhering to a certification program200. The certification module 114 may determine whether a participatinguser of the one or more participating users 214 has completed allhealthcare certification tasks 228(1)-(6) or task groups 222(1)-(6) thathave been due. In response to a participating user not being incompliance with a certification program 200 (e.g., the participatinguser has not completed all of the healthcare certification tasks 228(1)of a task group 222(1) by the due date 226(1) of the task group 222(1)),the certification module 114 may move the participating user to aremedial task group 222(1)-(6), modify the certification program 200 forthe participating user to include one or more remedial task groups222(1)-(6), or the certification module 114 may enroll the participatinguser in a remedial certification program 200. The certification module114 may send a notification to an administering user in response to aparticipating user not being in compliance with a certification program200. The administering user may determine what remedial steps should betaken regarding the participating user.

In one embodiment, in response to an enrolled user completing thecertification program 200, the certification module 114 may issue acertification to the enrolled user. An enrolled user completing thecertification program 200 may include the user completing all taskgroups 222(1)-(5) in the task plan 220 of the certification program 200.Completing the certification program 200 may include the user completingthe last task group 222(6) of a branch in the task plan 220 of thecertification program 200. Completing the certification program 200 mayinclude completing a minimum number of task groups 222(1)-(6), aspecified portion of the task groups 222(1)-(6), or some other subset ofthe task groups 222(1)-(6) of the task plan 220 of the certificationprogram 200. The conditions required for completing a certificationprogram 200 may be stored and maintained by the certification module114.

In one embodiment, the certification module 114 may provide a userinterface (e.g., via the user device 120) for managing one or moreusers, certification programs 200, or other certification functionality.The user interface may display a representation of a user. Therepresentation may include the user's name, expiration date of acertification, or time until a certification expires. The user interfacemay display one or more participating users' 214 statuses regarding acertification program 200 the participating users 214 are enrolled it.The user interface may include one or more task groups 222(1)-(6) orhealthcare certification tasks 228(1)-(6) the participating user hascompleted or not yet completed. The user interface may display othercertification program data, such as a due date 226(1)-(6). In someembodiments, the certification module 114 may include a reminderconfiguration. The reminder configuration may indicate when to send amessage to a user to remind him or her about one or more task groups222(1)-(6) or healthcare certification tasks 228(1)-(6). The userinterface may display a representation of a user group. Therepresentation may include the group's name or identifier, one or moreusers pertaining to the group, characteristics of the user group (e.g.,specialty, etc.) the configurations of a certification program 200 thegroup is enrolled in (e.g., interval 212, etc.), or other groupinformation.

In some embodiments, data related to a user's certification in ahealthcare protocol 210 may be stored in the certification module 114.In some embodiments, the data related to a user's certification may bestored by the account module 112, and the certification module 114 maysend data to the account module 112 to update a user's account.

Encounter Records

In one embodiment, the server 110 may include an encounter module 116.The encounter module 116 may generate an encounter record. The encounterrecord may include data associated with a patient encounter. Theencounter module 116 may track one or more events that occur during thepatient encounter. The encounter module 116 may add the tracked eventsto the encounter record. Portions of the data of the encounter recordmay be used by other modules of the server 110.

FIG. 3 depicts one embodiment of an encounter record 300. The encounterrecord 300 may include header data 310. The header data 310 may includean encounter ID 302. The header data 310 may include a creation date314. The header data 310 may include an outcome 316. The header data 310may include a simulation indicator 318. In some embodiments, theencounter record 300 may include healthcare protocol data 320. Thehealthcare protocol data 320 may include a healthcare protocol ID 322.The healthcare protocol data 320 may include a healthcare protocol name324. The encounter record 300 may include event data 330. The event data330 may include one or more events 332. An event 332 may include atimestamp 334. An event 332 may include a user ID 336. An event 332 mayinclude a healthcare protocol stage 338. An 332 event may include anevent name 340.

In one embodiment, the encounter ID 312 may include a string of text.The encounter ID may uniquely identify the encounter record 300. Thecreation date 314 may include a timestamp of when the encounter record300 was generated. The creation date 314 may include a time, a date, orother data. In some embodiments, the outcome 316 may include a string oftext, a number, or other data. The outcome 316 may indicate an outcomeof the event. Example outcomes may include that the patient survived,the patient was stabilized, the patient entered a comatose state, thepatient died, or another outcome. In one embodiment, the simulationindicator 318 may include data to indicate whether the encounterassociated with the encounter record 300 was a simulation or an actualmedical encounter.

In some embodiments, the healthcare protocol ID 322 may include a stringof text. The healthcare protocol ID 322 may uniquely identify thehealthcare protocol used in the encounter. The healthcare protocol name324 may include a string of text that includes the name of thehealthcare protocol used.

In one embodiment, the timestamp 334 may include a timestamp of when thecorresponding event 332 occurred. The timestamp may include a date,time, or other data. The user ID 336 may include data identifying userthat performed the event 332, witnessed the event 332, or was otherwiseinvolved in the event. In some embodiments, an event 332 may includemultiple user IDs 336. The healthcare protocol stage 338 may includedata identifying a stage of the healthcare protocol identified by thehealthcare protocol ID 322. In some embodiments, a healthcare protocolmay include one or more stages, and each stage may include one or moresteps for a healthcare worker to perform. The healthcare protocol stage338 may include the stage of the healthcare protocol that was occurringwhen the event 332 occurred. The event name 340 may include a string oftext. The event name 340 may describe the event. The event name 340 mayinclude “cardiac arrest,” “established IV access,” “check pulse,”“patient stabilized,” or another event name.

In some embodiments, an element of the encounter record 300 may belocated in a different portion or section of the encounter record 300than as described above or shown in FIG. 3. An encounter record 300 mayinclude other elements than those described above.

In one embodiment, the encounter module 116 may generate at least aportion of an encounter record 300 during a patient encounter. Theencounter module 116 may generate the encounter record 300 in responseto a command or in response to receiving input data from a client device120 of a healthcare worker participating in the patient encounter. Theencounter module 116 may automatically generate the encounter record 300in response to detecting a medical event.

In some embodiments, the encounter module 116 may add an event 332 to anencounter record 300. The encounter module 116 may add the event 332 inresponse to a user creating the event 332 or may automatically createthe event 332 and add the event 332 to the encounter record 300. In oneexample, after an encounter with a patient, a healthcare worker may usehis or her client device 120 to input information related to theencounter to generate the event 332. In another example, the encountermodule 116 may receive data from an EHR database related to patientencounter to generate the event 332. In yet another example, theencounter module 116 may receive data from a medical apparatus (e.g., anelectrocardiograph machine) that indicates a certain event to generatethe event 332.

In some embodiments, one or more portions of the encounter record 300may include data in an Extensible Markup Language (XML) format, aJavaScript Object Notation (JSON) format, or other data format.

Adaptive Healthcare Protocol Walkthroughs

In one embodiment, the server 110 may include a walkthrough module 118.The walkthrough module 118 may include one or more healthcare protocolwalkthroughs. A healthcare protocol walkthrough may include a series ofsteps a user may follow in order to perform a healthcare protocol. Thewalkthrough module 118 may display the series of steps to a user via theclient device 120. The walkthrough module 118 may determine whether auser complies with at least a portion of the healthcare protocol. Insome embodiments, the walkthrough module 118 may modify a healthcareprotocol walkthrough based on received data, outcomes of a step of thewalkthrough, or other data.

FIG. 4 depicts one embodiment of a healthcare protocol walkthrough 400.The healthcare protocol walkthrough 400 may include data that may assista healthcare worker in following a healthcare protocol. The healthcareprotocol walkthrough 400 may include header data 410. The header data410 may include a healthcare protocol name 412. The header data 410 mayinclude other information about the healthcare protocol walkthrough 400.The healthcare protocol walkthrough 400 may include one or more stages420. The one or more stages 420 may divide up the steps of a healthcareprotocol into logical or conceptual groups. A stage 420 may include aname 422. A stage 420 may include one or more symptoms 424. A stage 420may include one or more steps 426. A step 426 may correspond to anaction that a user following the healthcare protocol may take. A step426 may include a corresponding level of recommendation. A stage 420 mayinclude one or more outcomes 428. An outcome 428 may include one or moreconditions that may result from the steps 426 of the stage 420. Anoutcome 428 may include a corresponding next stage 420.

In one embodiment, the healthcare protocol name 412 may include a stringof text that may identify the healthcare protocol. For example, asdepicted in FIG. 4, the healthcare protocol name 412 of the healthcareprotocol 400 includes “Bradycardia with a Pulse.” In some embodiments,the stage name 422 may include a string of text that may identify thestage 420. For example, the stage 420(1) includes a name 422(1) thatincludes “Initial Management.” The one or more symptoms 424 of a stage420 may include a string of text or other data. The symptoms 424 mayinclude one or more outcomes of a previous stage 420.

In some embodiments, the one or more steps 426 may include a string oftext that indicates an action a healthcare worker may take. For example,the one or more steps 426(1) of the stage 420(1) include “Assess forhemodynamic compromise” and “Obtain 12 lead ECG.”

In one embodiment, one or more steps 426 may include a level ofrecommendation corresponding to the step 426. A recommendation level mayindicate the appropriateness of the step 426. The recommendation levelof a step 426 may include a range from “required” to “prohibited.” Inone embodiment, a step 426 may include a recommendation level of“required.” A “required” step 426 may include a step 426 that shouldalways be performed. A recommendation level may include “recommended.” A“recommended” step 426 may include a step 426 that is usuallyappropriate for the healthcare protocol, that is best-practice, thatshould almost always be done, or that are the standard of care for thehealthcare protocol. A step 426 may include a recommendation level of“possible.” A “possible” step 426 may include a step 426 that issometimes appropriate. A “possible” step 426 may include a step 426 thatis permissible based on factors such as patient presentation, caresetting, resource availability, healthcare worker experience, or otherfactors. A step 426 may include a recommendation level of “notrecommended.” A “not recommended” step 426 may include a step 426 thatis rarely appropriate, generally avoided, should not be performed underusual circumstances. A “not recommended” step 426 may include a step 426that, based on patient presentation, is likely to offer no benefit ormay even be potentially harmful. However, a “not recommended step” 426may be appropriate in some limited situations. A recommendation level of“prohibited” may include a step 426 that should not be performed underany circumstances. In some embodiments, when a healthcare protocolwalkthrough 400 is displayed to a user, each step 426 may indicate itslevel of recommendation (e.g., with a color, symbol, or otherindicator).

As an examples of a healthcare protocol walkthrough 400 for a cardiacarrest response, a first step 424 may include “Defibrillate after rhythmrecognition,” and the first step 424 may include a “required” level ofrecommendation.” A second step 424 may include “Administer Epinephrineevery 3-5 minutes,” the second step 424 may occur after the first step424, and the second step 424 may include a recommendation level of“possible.” A third step 424 may include “Administer Epinephrine,” thethird step 424 may occur before the first step, and the third step 424may include the level of recommendation of “not recommended.”

In some embodiments, in response to a first outcome 428 of a first stage420(1), the healthcare protocol walkthrough 400 may continue on to asecond stage 420(2), and in response to a second outcome of the one ormore steps 424(1) of the first stage 420(1), the healthcare protocolwalkthrough 400 may continue on to a third stage 420. For example, asdepicted in FIG. 4, after a healthcare worker performs the steps 426(1)of the initial management stage 420(1), the patient may experiencestable bradycardia. In response, the outcomes 428 may lead to the stablebradycardia stage 420(2). In response to the patient experience unstablebradycardia, the path 426 may lead to the unstable bradycardia stage 420(not depicted in FIG. 4). In some embodiments, in response to a stage420 including multiple possible outcomes 428, a healthcare protocolwalkthrough 400 may branch to different stages 420. The symptoms 424 ofone stage may correspond to an outcome 428 of another stage, which mayresult in different stages 420 leading to other stages 420. In someembodiments, the symptoms 424 and outcomes 428 of the stages 420 of ahealthcare protocol walkthrough 400 may result in the stages 420 forminga tree (e.g., a decision tree) or a graph.

In some embodiments, the walkthrough module 118 may receive, from auser, a command to initiate a healthcare protocol walkthrough 400. Thewalkthrough module 118 may display data related to the healthcareprotocol walkthrough 400 via the client device 120, such as the steps426(1) of the first stage 420(1) of the healthcare protocol walkthrough400. In some embodiments, the walkthrough protocol 116 may receive inputdata indicating one or more symptoms of a patient. The input data maycome from the user (e.g., entering the data via the client device 120),an EHR database, a medical apparatus connected to the patient (e.g., anelectrocardiograph machine), or another data source. In response to thereceived data, the encounter module 116 may determine an appropriatehealthcare protocol walkthrough 400 for the patient and may display theselected healthcare protocol walkthrough 400 to the user.

In some embodiments, the walkthrough module 118 may display a healthcareprotocol walkthrough 400 to multiple client devices 120. The walkthroughmodule 118 may display the healthcare protocol walkthrough 400 to themultiple client devices 120 simultaneously or at different times. Forexample, an emergency medical technician (EMT) may access thewalkthrough module 118 via his or her client device 120, receive ahealthcare protocol walkthrough 400, and display the healthcare protocolwalkthrough 400 on the client device 120. The EMT may be located in anambulance that is transporting a patient to a hospital. The EMT mayperform some of the steps 426 of the healthcare protocol walkthrough 400while in the ambulance. The walkthrough module 118 may track which steps424 the EMT has performed. When the ambulance arrives at the hospital,the EMT may hand off the patient to an emergency room doctor. Theemergency room doctor may use his or her client device 120 to access thewalkthrough module 118. The emergency room doctor may receive thehealthcare protocol walkthrough 400, and the healthcare protocolwalkthrough 400 may show where the EMT left off in the steps 426 of thehealthcare protocol walkthrough 400.

In one embodiment, the walkthrough module 118 may modify a healthcareprotocol walkthrough 400 based on received data. Modifying thehealthcare protocol walkthrough 400 may include adding a stage 420, step426, outcome 428, or other data to the healthcare protocol walkthrough400; removing a stage 420, step 426, outcome 428, or other data from thehealthcare protocol walkthrough 400; or modifying a stage 420, step 426,outcome 428, or other data of the healthcare protocol walkthrough 400.In some embodiments, modifying a step 426 may include modifying the stepaction or level of recommendation of the step 426. The received data mayinclude patient data (e.g., age, medical history, etc.) or other data.The modification of the healthcare protocol walkthrough 400 may be atemporary modification (e.g., only for the current instance of treatingthe patient).

In some embodiments, the walkthrough module 118 may retrieve healthcareprotocol external data from outside the server 110. The walkthroughmodule 118 may modify or update a healthcare protocol walkthrough 400based on the received data. For example, a healthcare governing body maydetermine that a certain step 426 in a healthcare protocol 400 isineffective or dangerous. The server 110 may receive data from acomputing device of the governing body related to the determination, andin response, the walkthrough module 118 may remove the step 426 or maymark the step as “not recommended.”

FIG. 5 depicts one embodiment of a user interface for a client device120. The user interface may display a healthcare protocol walkthrough400. The user interface may include a header area 502. The header area502 may include the name 412 of the healthcare protocol of thehealthcare protocol walkthrough 400. The header area 502 may includeother information such as a category 504 for the healthcare protocol(e.g., as depicted in FIG. 5, the healthcare protocol with the name 412“Tachycardia: Adult” may belong to the category 504 “AdvancedCardiovascular Life Support”).

In one embodiment, the user interface may include a clock area 506. Theclock area 506 may include a timer. The timer may display how long ahealthcare provider has been administering the healthcare protocol onthe patient.

The user interface may include a steps area 508. The steps area 508 mayinclude one or more stages 420(1)-(4). Each stage 420 may include one ormore steps 426. In some embodiments, a stage 420 may be collapsible onthe user interface such that only a portion of the steps 426 are visibleon the user interface. For example, as depicted in FIG. 5, the stages420(1), 420(2), and 420(4) are collapsed, and their steps 426 are notvisible. However, the stage 420(3) is expanded, and its steps 426(3) arevisible on the user interface. In some embodiments, the outcome of astage 420 or step 426 may be displayed on the user interface. Forexample, as depicted in FIG. 5, the outcome of the first stage 420(1) is“Stable,” and the outcome of the second stage 420(2) is “Regular.” Theuser interface may also display whether a stage 420 is in progress. Insome embodiments, the user interface may display whether a step 426 hasbeen completed or an outcome of a step 426. The user interface maydisplay a level of recommendation for a step 426.

In one embodiment, the user interface may include an auxiliaryinformation area 510. The auxiliary information area 510 may include avariety of information. For example, as depicted in FIG. 5, theauxiliary information area 510 may display patient information, such asage, sex, known medical conditions, current medications, or otherpatient data. In some embodiments, the auxiliary information are 510 maydisplay other data, such as more details about a stage 420, step 426,outcome of a stage 420 or step 426, or other data.

Certification through Experience

FIG. 6 depicts one embodiment of a system 600. The system 600 mayprovide a user the capability to work toward or maintain certificationin a healthcare protocol in response to participating in a trainingscenario or an actual medical episode. The system 600 may include one ormore components of the system 100 such as the certification module 114,encounter module 116, walkthrough module 118, or the client device 120.

In some embodiments, a training scenario or actual medical episode maybegin, and a user using the client device 120 may request 602 ahealthcare protocol 400 from the walkthrough module 118. The walkthroughmodule 118 may receive 604 data from an EHR database 606. Based on thedata received from the client device 120 or the EHR database 606, thewalkthrough module 118 may select or customize a healthcare protocolwalkthrough 400 and send 608 the healthcare protocol walkthrough 400 tothe client device 120. The user may follow the one or more steps 426 ofthe healthcare protocol walkthrough 400. Either during or after thetraining scenario or actual medical episode, the client device 120 maysend 610 data to the encounter module 116. The sent data may includedata indicating whether the user performed one or more steps 426 of thehealthcare walkthrough 400, how well the user performed the one or moresteps 426, or other data. The client device 120 may send 612 data to theEHR database 606. The encounter module 116 may generate an encounterrecord 300 based on the data received 610. The encounter module 116 mayreceive 610 data indicating whether the user performed a step 426 of thehealthcare protocol walkthrough 400 and may generate an event 332 basedon that data. The encounter module 116 may send 614 the encounter record300 to an encounter database 616. The encounter database 616 may storeone or more encounter records 300. The encounter database 616 may send618 encounter data to the certification module 114. The encounter datamay include an encounter record 300, a portion of an encounter record300, or other encounter data. Based on the encounter data sent 618 bythe encounter database, the certification module 114 may determinewhether an event 332 of the encounter data contributes, at least inpart, to a participating user completing a healthcare certification task228(1)-(6) of a certification program 200.

In one embodiment, the request sent 602 from the client device to thewalkthrough module 118 may include patient data (e.g., age, sex, patientID, etc.). The walkthrough module 118 may customize the healthcareprotocol walkthrough 400 based on the patient data (and other data, suchas the data received 604 from the EHR database 606). In someembodiments, a client device 122 other than the client device 120 usedby the user (e.g., a client device 112 used by a supervising physician)may send 610 at least a portion of the data. In some embodiments,another device (e.g., such as the EHR database 606, a electrocardiograph(ECG) device 124, etc.) may send 610 at least a portion of the data. Insome embodiments, the client device 120 may send 610 portions of thedata at different times during the training scenario or actual medicalepisode. Although FIG. 6 depicts the other client device 122, the EHRdatabase 606, and the ECG device 124 sending 610 data along with thedata from the client device 120, each of the other client device 122,the EHR database 606, and the ECG device 124 may send their respectivedata separately from the client device 120 or from each other.

The certification module 114 may determine whether an event 332contributes, at least in part, to a participating user of the one ormore participating users 214 completion of a healthcare certificationtask 228(1)-(6) of a certification program 200 in a variety of ways. Inone embodiment, the certification module 114 may include an event-taskmapping. The event-task mapping may include a data structure that mapsone or more events 332 of an encounter record 300 with one or morehealthcare certification tasks 228(1)-(6) of a certification program226. In one embodiments, the certification module 114 may include arules engine. The rules engine may include software that determineswhether an event 332 contributes, at least in part, to a participatinguser completing a healthcare certification task 228(1)-(6).

In one embodiment, the certification module 114 may determine how a anevent 332 may contribute to fulfilling a healthcare certification task228(1)-(6). The certification module 114 may determine this based on oneor more factors such as outcome of an actual medical episode (e.g.,whether the user performing CPR on the patient resulted in the patientbeing resuscitated). The certification module 114 may determine howclosely the user followed the one or more steps of the healthcareprotocol walkthrough 400. The certification module 114 may use otherfactors or data. In some embodiments, the certification module 114 maydetermine that an event may contribute more (e.g., with a higher orbetter value) in response to the user having a successful outcome of anactual medical episode, in response to the user more closely followingthe one or more steps 426 the healthcare protocol walkthrough 400, or inresponse to the difficulty of the training scenario or actual medicalepisode.

In some embodiments, the certification module 114 may determine whetherevent 332 may contribute to fulfilling a healthcare certification task228(1)-(6) for a user. Based on one or more configurations of the system100 or 600, of the user's account, or other factors, the certificationmodule 114 may determine which events 332 contribute and which events donot. For example, in one embodiment, the certification module 114 may beconfigured such that each event 332 contributes to fulfilling ahealthcare certification task 228(1)-(6). In another embodiment, thecertification module 114 may be configured such that only certain,specified events 332 contribute to a specified user's fulfillment of ahealthcare certification task 228(1)-(6). In other embodiments, thecertification module 114 may be configured such that only one out ofevery three events 332 for a specific user contribute to fulfilling thatuser's healthcare certification tasks 228(1)-(6).

In some embodiments, the certification module 114 may determine that anevent 332 contributes to fulfilling a healthcare certification task228(1) for a user only in response to the user currently being assigneda task group 222(1) with that healthcare certification task 228(1). Forexample, referring to FIG. 2B, a participating user of the one or moreparticipating users 214 may currently be working on the healthcarecertification tasks 228(2) of the task group 222(2). The participatinguser may resuscitate a patient using CPR during an actual medicalepisode. The encounter module 116 may generate an encounter record 300based on the medical episode. The encounter module 116 may send theencounter record 300 to the certification module 114. The certificationmodule 114 may include an event-task mapping that results in a CPR event332 contributing to fulfilling a demonstrating CPR healthcarecertification task 228(2), such as the “Demonstrate CPR basics ontraining mannequin” task of the one or more healthcare certificationtasks 228(5) of the task group 222(5). However, because theparticipating user is currently working on task group 222(2) and not222(5), the event 332 of resuscitating the patient during the actualmedical may not contribute to the participating user fulfilling thehealthcare certification task 228(5). In other embodiments, thecertification module 114 may be configured such that an event 332 maycontribute to a user fulfilling a healthcare certification task 228(5)of a task group 222(5) that the participating user is not currentlyassigned to. Other methods of certification module 114 determine whetheran event 332 contributes to fulfilling a healthcare certification task228(1)-(6) may also be used.

One embodiment may include a system. The system may include the server110. The system may include a processor. The system may include acomputer-readable storage medium. The computer-readable storage mediummay include one or more machine-readable instructions that, whenexecuted by the processor, cause the processor to perform one or moresteps. In some embodiments, the computer-readable storage medium mayinclude a computer memory, a persistent computer storage device (such asflash memory or a hard disk drive), or some other type of storagemedium. In some embodiments, the machine-readable instructions mayinclude the account module 112, the certification module 114, theencounter module 116, the walkthrough module 118, or some othermachine-readable instructions.

In one embodiment, the one or more steps performed by the processor mayinclude receiving, at a server, a request for a healthcare protocolwalkthrough. The one or more steps may include generating, at theserver, the requested healthcare protocol walkthrough. The healthcareprotocol walkthrough may include one or more stages. The healthcareprotocol walkthrough may include one or more steps. Each stage of theone or more stages may include at least one step of the one or moresteps. The one or more steps may include sending, to a client device, atleast a portion of the generated healthcare protocol walkthrough. Theone or more steps may include receiving healthcare event data. The oneor more steps may include determining whether a healthcare event of thehealthcare event data contributes to fulfilling a healthcarecertification task of a certification program.

In some embodiments, the server may include the server 110. Thehealthcare protocol walkthrough may include a healthcare protocolwalkthrough 400. The one or more stages may include one or more stages420(1)-(n) of the healthcare protocol walkthrough 400. The one or moresteps may include one or more steps 426(1)-(n) of the healthcareprotocol walkthrough 400. The client device may include a client device120, 122. The healthcare event data may include event data 330. Thehealthcare event may include events 332(1)-(n). The healthcarecertification task may include a healthcare certification task 228(1).The certification program may include a certification program 200.

In one embodiment, sending, to the client device 120, 122, the at leasta portion of the generated healthcare protocol walkthrough 400 mayinclude sending the at least a portion of the generated healthcareprotocol walkthrough 400 to one or more client devices 120, 122. In someembodiments, receiving the healthcare event data 330 may includereceiving the healthcare event data 330 from the client device 120, 122,an EHR database 606, or a medical device.

In one or more embodiments, receiving the healthcare event data 330 mayinclude receiving data that includes an indication that the healthcareevent 332(1) of the healthcare event data 330 corresponds to asimulation, or that corresponds to an actual medical episode.

In some embodiments, determining whether the healthcare event 332(1) ofthe healthcare event data 330 contributes to fulfilling the task 228(1)of the certification program 200 may include making the determinationbased on an event-task mapping. The event-task mapping may include amapping of a healthcare event 332(1) to a task 228(1) of thecertification program 200. At least a portion of the event-task mappingmay be based on data received from a patient safety organization (PSO).In some embodiments, the one or more steps may further includeanonymizing the healthcare event data 330 and sending the anonymizedhealthcare event data 330 to a PSO.

In some embodiments, the one or more steps may include, in responsedetermining whether the healthcare event 332(1) of the healthcare eventdata 330 contributes to fulfilling the task 228(1) of the certificationprogram 200, determining an amount that the healthcare event 332(1)contributes to fulfilling the task 228(1). In one embodiment, the amountmay be based on a compliance with a healthcare protocol associated withthe certification program 200, an outcome included in the healthcareevent data 330 or the encounter record 300 associated with the eventdata 330, or a review by a healthcare worker received by the system.

Computer-Implemented Methods

FIG. 7 depicts one embodiment of a method 700. The method 700 mayinclude a computer-implemented cardiopulmonary resuscitation (CPR)certification method. In one embodiment, the method 700 may includeobtaining 702, at a server a user input from a user interface. The userinput may define an interval for a desired CPR certification schedule.The method 700 may include generating 704, at the server, a CPRcertification program. Generating 704 the CPR certification program mayinclude generating two or more task groups. Each task group may includea healthcare certification task. The method 700 may includeadministering, at the server, the CPR certification program.Administering the CPR certification program may include assigning 706,at the interval defined by the user input, one task group of the two ormore task groups to a user that may be enrolled in the CPR certificationprogram. Administering the CPR certification program may includereceiving 708 an indication that the enrolled user has completed thehealthcare certification task of the assigned one task group.

In one embodiment, the certification module 114 may perform at least aportion of the steps 702-708 of the method 700. A certification program200 may include the CPR certification program. In some embodiments,obtaining 702, at the server, the user input from the user interface mayinclude receiving the user input at the server 110. The client device120 may receive the user input from a user and may send the user inputthrough the data network 130 to the server 110. The user input definingthe interval for the desired CPR certification schedule may include avalue to be used as the interval 212 of a certification program 200.

In one embodiment, generating 704 the CPR certification program mayinclude generating a certification program 200. The certificationprogram 200 may include a healthcare protocol 210 of “CPR.” Generatingthe two or more task groups may include generating two or more of thetask groups 222(1)-(n) of the task plan 220 pertaining to thecertification program 200. The one or more healthcare certificationtasks of each of the two or more task groups may include one or morehealthcare certification tasks 228(1)-(n).

In some embodiments, assigning 706, at the interval defined by the userinput, one task group of the two or more task groups to a user enrolledin the CPR certification program may include assigning a task group222(1) to a participating user of the participating users 214 of thecertification program 200. The certification module 114 may track usersenrolled in the certification program 200 to determine which task groups222(1)-(n) are assigned to which users, which users have completed oneor more healthcare certification tasks 228(1)-(n) of the task groups222(1)-(n), or other functionality related to users as described above.

In one or more embodiments, receiving 708 the indication that theenrolled user has completed the healthcare certification task of theassigned one task group may include the certification module 114receiving data from the server 110, the client device 120, or anotherdevice indicating that the enrolled user has completed a healthcarecertification task 228(1). The data may include data indicating whethera user viewed a video, whether a user properly performed on a trainingmannequin, or whether a user earned a certain score on a test, orwhether a user performed some other healthcare certification task228-completing action.

In one embodiment, generating the two or more task groups may includecustomizing the two or more task groups based on a specialty of a userenrolled in the CPR certification program. For example, as discussedabove, to which branch the participating user may be assigned may bebased on one or more characteristics of the participating user. Thecertification module 114 may obtain the specialty of the enrolled userfrom the accounts module 112 or from some other source. As anotherexample discussed above, users enrolled in the CPR certification programmay all include the same specialty (e.g. emergency room doctors), andthe certification program 200 associated with that group may include oneor more task groups 222(1)-(n) selected for that specialty.

In some embodiments, the method 700 may further include obtaining, atthe server, the healthcare certification task from the American RedCross. For example, the server 110 may receive a data representation ofa healthcare certification task 228(1) over the data network 130 from aserver or other computing device operated by the American Red Cross. Thehealthcare certification task 228(1) may be received by thecertification module 114. The healthcare certification task 228(1) maybe added to the library of healthcare certification tasks 228(1)-(6).

In one or more embodiments, administering the CPR certification programmay further include, in response to the user completing the two or moretask groups, issuing a CPR certification to the user. The usercompleting the two or more task groups may include the user completingthe required healthcare certification tasks 228(1)-(6) of the two ormore task groups 222(1)-(6) between the respective start dates224(1)-(6) and respective end dates 226(1)-(6) of the two or more taskgroups 222(1)-(6) as discussed above, or may include some other actionrequired by the certification program 200 to complete the two or moretask groups.

FIG. 8 depicts one embodiment of a method 800. The method 800 mayinclude a computer-implemented method. In one embodiment, the method 800may include obtaining 802, at a computing device, an input that definesan interval for assigning task groups to an enrolled user. The method800 may include obtaining 804, at the computing device, a selection ofone or more healthcare certification tasks. The method 800 may includegenerating 806, at the computing device, one or more task groups. A taskgroup of the one or more task groups may include a healthcarecertification task of the one or more healthcare certification tasks.The method 800 may include generating 808, at the computing device, acertification program corresponding to a healthcare protocol, andassociating the one or more task groups with the certification program.

In some embodiments, the method 800 may include administering, at thecomputing device, the certification program. Administering thecertification program may include, in response to the arrival of a firststart date, assigning 810, via the computing device, the task group tothe enrolled user enrolled in the certification program. Administeringthe certification program may include receiving 812, at the computingdevice, an indication that the enrolled user has completed thehealthcare certification task of the task group.

In one or more embodiments, the computing device may include the server110. The interval for assigning task groups may include the interval212. The enrolled user may include a participating user of theparticipating users 214. The one or more healthcare certification tasksmay include the healthcare certification tasks 228(1)-(6). The one ormore task groups may include task groups 222(1)-(6). The certificationprogram may include a certification program 200.

In one embodiment, obtaining 804 the selection of the one or morehealthcare certification tasks may include obtaining a selection ofhealthcare certification tasks 228(1)-(6) from a library of healthcarecertification tasks stored by the certification module 114. In someembodiments, a certification administrator may select the healthcarecertification tasks 228(1)-(6) and the certification module 114 mayreceive the selection of healthcare certification tasks 228(1)-(6). Inanother embodiment, the certification module 114 may automaticallygenerate at least a portion of a certification program 200, which mayinclude automatically selecting the one or more healthcare certificationtasks 228(1)-(6), as described above.

In one embodiment, generating 806 the one or more task groups mayinclude customizing the one or more task groups 222(1)-(6) based on aspecialty of the enrolled user. In some embodiments, customizing the oneor more task groups 222(1)-(6) based on the specialty of the enrolleduser may include selecting a healthcare certification task 228(1) fromthe one or more healthcare certification tasks 228(1)-(6) based on thespecialty of the enrolled user, and including the selected healthcarecertification task 228(1) with the task group 222(1) of the one or moretask groups 222(1)-(6).

In some embodiments, generating 806 the one or more task groups mayinclude receiving, via user input received from a user interface, aselection of the healthcare certification task 228(1) from the one ormore healthcare certification tasks 228(1)-(6) for inclusion with thetask group 222(1) of the one or more task groups 222(1)-(6). In oneembodiment, generating 806 the one or more task groups may include thecomputing device automatically selecting the healthcare certificationtask 228(1) from the one or more healthcare certification tasks228(1)-(6) for inclusion with the task group 222(1) of the one or moretask groups 222(1)-(6).

In one or more embodiments, assigning 810 the task group of the one ormore task groups to the enrolled user may include assigning the taskgroup 222(1) to the one or more enrolled users of the enrolled usersgroup 214. In one embodiment, the enrolled users group 214 may includeone or more users that include a common characteristic. The commoncharacteristic may include a specialty, a healthcare worker position, orwhether the enrolled users group includes one or more healthcareworkers.

FIG. 9 depicts one embodiment of a method 900. The method 900 mayinclude a computer-implemented method. The method 900 may includeobtaining 902, at a server, an input that defines an interval forassigning task groups to an enrolled user. The method 900 may includeobtaining 904, at the server, a selection of one or more healthcarecertification tasks. The method 900 may include generating 906, at theserver, one or more task groups. A task group of the one or more taskgroups may include a healthcare certification task of the one or morehealthcare certification tasks.

The method 900 may include generating 908 one or more trigger events. Atrigger event of the one or more trigger events may include a conditionand data linking a first task group of the one or more task groups to asecond task group of the one or more task groups. The method 900 mayinclude generating 910, at the server, a certification programcorresponding to a healthcare protocol. Generating 910 the certificationprogram may include associating the one or more task groups with thecertification program. The method 900 may include administering, at theserver, the certification program. Administering the certificationprogram may include, in response to the arrival of a first start date,assigning 912 the first task group to the enrolled user enrolled in thecertification program. Administering the certification program mayinclude, in response to fulfillment of the condition of the triggerevent of the first task group, assigning 914 the second task group tothe enrolled user.

In some embodiments, the server may include the server 110. The intervalfor assigning task groups may include the interval 212. The one or morehealthcare certification tasks may include the healthcare certificationtasks 228(1)-(6). The one or more task groups may include task groups222(1)-(6). The one or more trigger events may include the triggerevents 230(1)-(2). The certification program may include a certificationprogram 200. The first start data may include the start date 224(1). Thefirst task group may include the task group 222(1). The second taskgroup may include the task group 222(2).

In one embodiment, the condition may include the enrolled usercompleting at least a portion of the healthcare certification tasks228(1) of the first task group 222(1). In some embodiments, thecondition may include an arrival of a due date 226(1) of the first taskgroup 222(1). In one embodiment, the condition may include the enrolleduser earning below a threshold score on a healthcare certification task228(1) of the first task group 222(1). In one or more embodiments, thecondition may include a specialty of the enrolled user.

FIG. 10 depicts one embodiment of a method 1000. The method 1000 mayinclude a computer-implemented cardiac arrest response walkthroughmethod. In one embodiment, the method 1000 may include receiving 1002,at a server, a request for a cardiac arrest response walkthrough. Themethod 1000 may include receiving 1004, at the server, patient dataassociated with a patient. The patient data may include data describinga characteristic of the associated patient.

In some embodiments, the method 1000 may include generating 1006, at theserver, the cardiac arrest response walkthrough. The cardiac arrestresponse walkthrough may include one or more cardiac arrest responsesteps. The server may customize the one or more cardiac arrest responsesteps based on the patient data. The method 1000 may include sending1008, to a client device, the cardiac arrest response walkthrough. Themethod 1000 may include receiving 1010 healthcare event data thatdescribes a cardiac arrest medical episode with the patient. The method1000 may include generating 1012 an encounter record based on thereceived healthcare event data. The encounter record may include one ormore cardiac arrest events associated with the patient.

In one or more embodiments, the server may include the server 110. Insome embodiments, the encounter module 116 or the walkthrough module 118may perform one or more of the steps 1002-1012 of the method 1000. Thecardiac arrest response walkthrough may include a healthcare protocolwalkthrough 400. The healthcare protocol name 412 may include cardiacarrest. In one embodiment, the patient data may include the patientinformation that may be displayed in the auxiliary information area 510.The patient data may be sent by an EHR database 606, a client device120, 122, or by another data source. The one or more cardiac arrestresponse steps may include one or more steps 426(1)-(n). The healthcareevent data may include the event data 330 of an encounter record 300.The one or more cardiac arrest events may include one or more events332(1)-(n).

In some embodiments, receiving 1002 the request for the cardiac arrestresponse walkthrough may include receiving the request from a mobiledevice of a healthcare worker. The mobile device may include a clientdevice 120. In one embodiment, receiving 1004 the patient dataassociated with the patient may include receiving the patient data fromthe mobile device. In one or more embodiments, customizing the one ormore cardiac arrest response steps based on the patient data may includethe server 110 customizing the one or more cardiac arrest response steps426(1)-(n) based on the patient's age.

In one embodiment, the encounter record, which may include the encounterrecord 300, may include data indicating the encounter record 300 isassociated with a cardiac arrest healthcare protocol (i.e., thehealthcare protocol name 324 may include “Cardiac Arrest”) and anoutcome 316 of the cardiac arrest medical episode. In some embodiments,the method 1000 may further include determining, based on an event-taskmapping, whether a healthcare event 332(1) of the healthcare event data330 contributes to fulfilling a healthcare certification task 228(1) ofa cardiac arrest certification program 200.

FIG. 11 depicts one embodiment of a method 1100. The method 1100 mayinclude a computer-implemented method. The method 1100 may includereceiving 1102, at a server, a request for a healthcare protocolwalkthrough. The method 1100 may include generating 1104, at the server,the requested healthcare protocol walkthrough. The healthcare protocolwalkthrough may include one or more stages. The healthcare protocolwalkthrough may include one or more steps. Each stage of the one or morestages may include at least one step of the one or more steps.

The method 1100 may include sending 1106, to a client device, at least aportion of the generated healthcare protocol walkthrough. The method1100 may include receiving 1108 healthcare event data. The method 1100may include generating 1110 an encounter record based on the healthcareevent data. The encounter record may include one or more healthcareevents.

In some embodiments, the server may include the server 110. Thehealthcare protocol walkthrough may include a healthcare protocolwalkthrough 400. The one or more stages may include one or more stages420(1)-(n) of the healthcare protocol walkthrough 400. The one or moresteps may include one or more steps 426(1)-(n) of the healthcareprotocol walkthrough 400. The client device may include a client device120, 122. The healthcare event data may include event data 330. Theencounter record may include an encounter record 300. The healthcareevents may include events 332(1)-(n).

In some embodiments, the method 1100 may further include receivingpatient data associated with a patient. Receiving the patient dataassociated with the patient may be similar to receiving 1004, at theserver, patient data associated with a patient as described in relationto the method 1000 of FIG. 10. Generating 1104 the requested healthcareprotocol walkthrough may further include selecting at least a portion ofthe one or more steps 426(1)-(n) based on the patient data.

In one or more embodiments, receiving the patient data associated withthe patient may include receiving the patient data from a client device120, 122 or an electronic health record (EHR) database 606. The patientdata associated with the patient may include the patient's age, thepatient's sex, or at least a portion of the patient's medical history.In some embodiments, receiving 1108 the healthcare event data mayinclude receiving the healthcare event data 330 from the client device120, 122, an EHR database 606, or a medical device. The medical devicemay include an electrocardiograph (ECG) device 124, a respiratorymonitoring device, a pacemaker, or some other type of medical device.

Some of the steps of the above-described methods 700, 800, 900, 1000,1100 have been described above. In some embodiments, other elements ofthe systems 100 or 600 may perform one or more of those steps, not justthose described in relation to the methods 700, 800, 900, 1000, 1100.For example, in some embodiments, a client device 120, 122 may performone or more of the steps of the method 700, 800, 900, 1000, 1100. In oneor more embodiments, a step of a method 700, 800, 900, 1000, 1100 mayinclude sub-steps or functionality described above in relation to FIGS.1-6, although not explicitly described in relation to FIGS. 7-11.

Misc

In some embodiments, a user of the system 100 may include a person thatworks at healthcare facility but does not access the system 100 himselfor herself but has another person (such as hospital support staff)access the system 100 on the user's behalf. For example, a janitor thatworks at a hospital may not use a client device 120 to interact with theserver 110, however a hospital support staff may use a client device 120to update the janitor's user account information, track the janitor'sprogress in maintaining certification in a healthcare protocol, orperform other system 100 functionality.

In some embodiments, a module (such as the account module 112,certification module 114, encounter module 116, walkthrough module 118,or other module) storing data may include the module storing the data inan area of a file system of the server 110 that the module controls. Inother embodiments, the module storing data may include the modulestoring data in a database. The database may be a database stored on theserver 110 or may include a database on another device.

In some embodiments, one or more modules of the server 110 may send datato an external data repository. The external data repository may includea PSO. Before the server 110 sends the data to the PSO, the server 110may strip the data of identifying information or other information suchthat the data complies with healthcare information regulation (e.g., theHealth Insurance Portability and Accountability Act (HIPAA)). In someembodiments, the data sent to the PSO may include a healthcare protocolused on a patient in an actual medical episode, the outcome of using thehealthcare protocol, or other data. The PSO may use the received data toimprove healthcare protocols, training, or other information. The PSOmay send updated healthcare protocol data to the server 110.

Computer Hardware and Software

As will be appreciated by one skilled in the art, aspects of the presentdisclosure may be embodied as an apparatus, system, method, computerprogram product, or the like. Accordingly, aspects of the presentdisclosure may take the form of an entirely hardware embodiment, anentirely software embodiment (including firmware, resident software,micro-code, etc.) or an embodiment combining software and hardwareaspects that may all generally be referred to herein as a “circuit,”“module,” or “system.” Furthermore, aspects of the present disclosuremay take the form of a computer program product embodied in one or morecomputer readable medium(s) having program code embodied thereon.

In some embodiments, a module may be implemented as a hardware circuitcomprising custom VLSI circuits or gate arrays, off-the-shelfsemiconductors such as logic chips, transistors, or other discretecomponents. A module may also be implemented in programmable hardwaredevices such as field programmable gate arrays, programmable arraylogic, programmable logic devices or the like.

Modules may also be implemented in software for execution by varioustypes of processors. An identified module of program code may, forinstance, comprise one or more physical or logical blocks of computerinstructions which may, for instance, be organized as an object,procedure, or function. Nevertheless, the executables of an identifiedmodule need not be physically located together but may comprisedisparate instructions stored in different locations which, when joinedlogically together, comprise the module and achieve the stated purposefor the module.

Indeed, a module of program code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set or may be distributed over differentlocations including over different storage devices, and may exist, atleast partially, merely as electronic signals on a system or network.Where a module or portions of a module are implemented in software, theprogram code may be stored and/or propagated on in one or more computerreadable medium(s).

The computer program product may include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out aspects of the present disclosure.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processor devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processor device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processor device.

Computer readable program instructions for carrying out operations ofthe present disclosure may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the C programminglanguage or similar programming languages. The computer readable programinstructions may execute on a supercomputer, a compute cluster, or thelike. The computer readable program instructions may execute entirely onthe user's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider). In some embodiments, electronic circuitry including, forexample, programmable logic circuitry, field-programmable gate arrays(FPGA), or programmable logic arrays (PLA) may execute the computerreadable program instructions by utilizing state information of thecomputer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present disclosure.

Aspects of the present disclosure are described herein with reference toflowchart illustrations or block diagrams of methods, apparatuses,systems, or computer program products according to embodiments of thedisclosure. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The schematic flow chart diagrams included herein are generally setforth as logical flow chart diagrams. As such, the depicted order andlabeled steps are indicative of one embodiment of the presented method.Other steps and methods may be conceived that may be equivalent infunction, logic, or effect to one or more steps, or portions thereof, ofthe illustrated method. Additionally, the format and symbols employedare provided to explain the logical steps of the method and areunderstood not to limit the scope of the method. Although various arrowtypes and line types may be employed in the flow chart diagrams, theyare understood not to limit the scope of the corresponding method.Indeed, some arrows or other connectors may be used to indicate only thelogical flow of the method. For instance, an arrow may indicate awaiting or monitoring period of unspecified duration between enumeratedsteps of the depicted method. Additionally, the order in which aparticular method occurs may or may not strictly adhere to the order ofthe corresponding steps shown.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and computerprogram products according to various embodiments of the presentdisclosure. In this regard, each block in the schematic flowchartdiagrams and/or schematic block diagrams may represent a module,segment, or portion of code, which comprises one or more executableinstructions of the program code for implementing the specified logicalfunction(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted concurrently, or the blocks may sometimes be executed in thereverse order, depending upon the functionality involved. Other stepsand methods may be conceived that are equivalent in function, logic, oreffect to one or more blocks, or portions thereof, of the illustratedFigures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and program code.

Other embodiments of the disclosure will be apparent to those skilled inthe art from consideration of the specification and practice of thedisclosure disclosed herein. It is intended that the specification andexamples be considered as exemplary only, with a true scope and spiritof the disclosure being indicated by the following claims.

1. A computer-implemented cardiac arrest response walkthrough method, comprising: receiving, at a server, a request for a cardiac arrest response walkthrough; receiving, at the server, patient data associated with a patient, wherein the patient data includes data describing a characteristic of the associated patient; generating, at the server, the cardiac arrest response walkthrough, wherein the cardiac arrest response walkthrough includes a plurality of cardiac arrest response steps, wherein each cardiac arrest response step of the plurality of cardiac arrest response steps includes a level of recommendation, wherein the level of recommendation is selected from the group consisting of required, recommended, possible, not recommended, and prohibited, and the server customizes the plurality of cardiac arrest response steps based on the patient data; sending, to a client device, the cardiac arrest response walkthrough; displaying, on the client device, the cardiac arrest walkthrough, wherein displaying the cardiac arrest walkthrough includes displaying at least a portion of the plurality of cardiac arrest response steps, and for each displayed cardiac arrest response step, displaying an indicator of the level of recommendation corresponding to the displayed cardiac arrest response step; receiving healthcare event data that describes a cardiac arrest medical episode with the patient, wherein receiving the healthcare event data includes providing, from an electrocardiograph (ECG) device, a real-time heartbeat of the patient, providing a timestamp of when the ECG device provided the real-time heartbeat, and generating the healthcare event data, including generating a cardiac arrest event that includes the timestamp and an event name, wherein the event name is based on the ECG-provided real-time heartbeat; and generating an encounter record based on the received healthcare event data, wherein the encounter record includes one or more cardiac arrest events associated with the patient.
 2. The computer-implemented method of claim 1, wherein receiving the request for the cardiac arrest response walkthrough comprises receiving the request from a mobile device of a healthcare worker.
 3. The computer-implemented method of claim 2, wherein receiving the patient data associated with the patient comprises receiving the patient data from the mobile device.
 4. The computer-implemented method of claim 1, wherein the server customizing the plurality of cardiac arrest response steps based on the patient data comprises customizing the plurality of cardiac arrest response steps based on the patient's age.
 5. The computer-implemented method of claim 1, wherein the encounter record further comprises: data indicating the encounter records is associated with a cardiac arrest healthcare protocol; and an outcome of the cardiac arrest medical episode.
 6. The computer-implemented method of claim 1, further comprising determining, based on an event-task mapping, whether a healthcare event of the healthcare event data contributes to fulfilling a healthcare certification task of a cardiac arrest certification program.
 7. A computer-implemented method, comprising: receiving, at a server, a request for a healthcare protocol walkthrough; generating, at the server, the requested healthcare protocol walkthrough, wherein the healthcare protocol walkthrough includes a plurality of stages, a plurality of steps, wherein each stage of the plurality of stages includes at least one step of the plurality of steps, and a plurality of outcomes, wherein each outcome corresponds to a first stage of the plurality of stages, each outcome includes a possible medical condition resulting from following the at least one step of the first stage of the plurality of stages, and each outcome includes a second stage of the plurality of stages, wherein the second stage includes a next stage in the healthcare protocol walkthrough in response to the possible medical condition; sending, to a client device, at least a portion of the generated healthcare protocol walkthrough; receiving healthcare event data; generating an encounter record based on the healthcare event data, wherein the encounter record includes one or more healthcare events, and wherein each healthcare event includes data representing a first user identifier corresponding to a first healthcare worker that performed at least one step of the plurality of steps of the generated healthcare protocol walkthrough, a second user identifier corresponding to a second healthcare worker that witnessed the first user perform the at least one step of the plurality of steps of the generated healthcare protocol walkthrough, and a medical event that occurred during a step of the plurality of steps of the healthcare protocol walkthrough; sending at least a portion of the encounter record to a certification module; and determining, by the certification module, for each healthcare event of the encounter record, whether the healthcare event contributes to fulfilling a healthcare certification task of a certification program that the first healthcare worker is enrolled in, wherein the certification module administers the certification program.
 8. The computer-implemented method of claim 7: further comprising receiving patient data associated with a patient; and wherein generating the requested healthcare protocol walkthrough further includes selecting at least a portion of the plurality of steps based on the patient data.
 9. The computer-implemented method of claim 8, wherein receiving the patient data associated with the patient comprises receiving the patient data from at least one of: a client device; or an electronic health record (EHR) database.
 10. The computer-implemented method of claim 8, wherein the patient data associated with the patient comprises at least one of: the patient's age; the patient's sex; or at least a portion of the patient's medical history.
 11. The computer-implemented method of claim 7, wherein receiving healthcare event data comprises receiving the healthcare event data from at least one of: the client device; an EHR database; or a medical device.
 12. The computer-implemented method of claim 11, wherein the medical device comprises at least one of: an electrocardiograph (ECG) machine; a respiratory monitoring device; or a pacemaker.
 13. A system, comprising: a processor; and a computer-readable storage medium including a plurality of machine-readable instructions that, when executed by the processor, cause the processor to perform the steps of receiving, at a server, a request for a healthcare protocol walkthrough, generating, at the server, the requested healthcare protocol walkthrough, wherein the healthcare protocol walkthrough includes a plurality of stages, a plurality of steps, wherein each stage of the plurality of stages includes at least one step of the plurality of steps, and a plurality of outcomes, wherein each outcome corresponds to a first stage of the plurality of stages, each outcome includes a possible medical condition resulting from following the at least one step of the first stage of the plurality of stages, and each outcome includes a second stage of the plurality of stages, wherein the second stage includes a next stage in the healthcare protocol walkthrough in response to the possible medical condition; sending, to a client device, at least a portion of the generated healthcare protocol walkthrough, receiving healthcare event data, generating a healthcare event based on the received healthcare event data, wherein the healthcare event includes data representing a user identifier corresponding to a first healthcare worker, and a medical event that occurred during a step of the plurality of steps of the healthcare protocol walkthrough, sending the healthcare event to a certification module, and determining, by the certification module, whether the healthcare event contributes to fulfilling a healthcare certification task of a certification program that the first healthcare worker is enrolled in, wherein the certification module administers the certification program.
 14. The system of claim 13, wherein sending, to the client device, the at least a portion of the generated healthcare protocol walkthrough comprises sending the at least a portion of the generated healthcare protocol walkthrough to a plurality of client devices.
 15. The system of claim 13, wherein receiving the healthcare event data comprises receiving the healthcare event data from at least one of: the client device; an EHR database; or a medical device.
 16. The system of claim 13, wherein the healthcare event data comprises an indication that the healthcare event data corresponds to a simulation.
 17. The system of claim 13, wherein determining, by the certification module, whether the healthcare event contributes to fulfilling the task of the certification program comprises providing, by the certification module, an event-task mapping, wherein the event-task mapping includes a mapping of a healthcare event to at least one task of a plurality of tasks of the certification program.
 18. The system of claim 17, wherein at least a portion of the event-task mapping is based on data received from a patient safety organization (PSO).
 19. The system of claim 17, further comprising: anonymizing the healthcare event data; and sending the anonymized healthcare event data to a PSO.
 20. The system of claim 13, wherein the plurality of machine-readable instructions cause the processor to further perform the step of, in response determining that the healthcare event contributes to fulfilling the task of the certification program, determining an amount that the healthcare event contributes to fulfilling the task, wherein the amount is based on at least one of: a compliance with a healthcare protocol of the certification program; an outcome included in the healthcare event; or a review by a second healthcare worker received by the system, wherein the second healthcare worker include a healthcare worker that witnessed the first user perform the at least one step of the plurality of steps of the healthcare protocol walkthrough. 